Tuning ldap server and directory database

ABSTRACT

A method and system for autonomously tuning a Lightweight Directory Access Protocol (LDAP) server are disclosed. The method comprises activating a tuning thread when defined conditions are met; and using this thread to initiate automatically a tuning procedure to tune an LDAP server cache, to tune a database buffer pool for the server, and to perform runtime tuning of parameters of the database. Tuning may be initiated upon reaching a specified time, or when the cache hit ratio of the server falls below a given threshold or on issuing the extended operation. The tuning procedure may include Basic or Advanced Tuning procedures and an Advanced Tuning procedure. The Basic Tuning procedure is comprised of static tuning of the server based on the number and size of entries in the database, and the Advanced Tuning Procedure is a real time procedure based on real client search patterns.

BACKGROUND

Light Weight Directory Access Protocol (LDAP) has become very populardue to its efficient and fast data access. A large number ofapplications/servers are currently being developed which use an LDAPdirectory as their centralized data repository. In the LDAP directory,data is stored as entries including key/value pairs. A key/value pairmay include an attribute name and an attribute value. For example, anentry for an attribute known as a file type attribute may include aspecific file type as the attribute name and the content of the file asthe attribute value.

Some file types may include a set of metadata stored inside the file.For example, jpeg photo Exchangeable Image File Format (EXIF) used forcompressed digital camera images includes multiple metadata fields fordescribing properties of an image stored in the file. These propertiesmay specify the date when the picture was taken, the camera model usedfor taking the picture, the vertical and horizontal size of the picture,etc. This additional information might be useful for performing searchesof the LDAP directory.

In order to maintain optimal performance, an LDAP server needs tuning atregular intervals based on the type of client requests, and type of datastored in the LDAP server database. Typically, administrators decide ona maintenance time, when they can analyze the tuning parameters andmanually adjust the values of several tuning parameters. The types oftuning performed by the administrators are: LDAP Server Tuning and LDAPServer Database Tuning.

LDAP Server Tuning monitors the cache hit and miss ratio for the clientsearch requests. This is done by monitoring several LDAP cachemonitoring parameters provided by the server. Based on this analysis,the value of LDAP cache is tuned. If the LDAP cache miss ratio is high,then the size of LDAP cache is increased. Note that LDAP cache and entrycache are used interchangeably, but both of them essentially mean thesame.

For improved performance of directory server, administrator needs totune the LDAP server database cache. In this tuning, the LDAP server anddatabase are stressed using some third party tools. Based on theanalysis report, the LDAP server database cache is tuned. The stressengine is run again to see if the throughput for SEARCH operations isimproved. If not, the LDAP server database cache is increased and thestressing cycle is run again. This cycle needs to be repeated untiloptimal search rate is observed. For example, SLAMD is a Sun onedirectory server stress tool which is used to stress the LDAP Server andgenerate an analysis report.

These tuning procedures, for example, involve a tot of manual efforts bythe administrators, and the administrators should be well educated onwhat/how/when of the tuning parameters to be tuned. Also, theadministrator needs to prepare the workload to be executed for analysisof tuning parameter. Workload is the design or the template that will befed into the stress engine. Further, the administrator needs to betrained on the stress engine toot that will be used to run the workload.

SUMMARY

Embodiments of the invention provide a method and system forautonomously tuning a Lightweight Directory Access Protocol (LDAP)server. It should be obvious to one skilled in the art that the methodcan be implemented by means of a computer program stored on a suitablemedia when the computer program is loaded and executed on the system.The method comprises activating a tuning thread when defined conditionsare met; and using said tuning thread to initiate automatically a tuningprocedure to tune an LDAP server cache, to tune a database buffer poolfor the server, and to perform runtime tuning of given parameters of theLDAP database. For example, the defined conditions may include reachinga specified time, or when the cache hit ratio of the server falls belowa given threshold value, or in response to a command issued by theadministrator (like an extended operation request).

The tuning procedure may include one or both of a Basic Tuning procedureand an Advanced Tuning procedure. The Basic Tuning procedure iscomprised of static tuning of the server based on the total number ofentries in the database and the average size of said entries. TheAdvanced Tuning Procedure is comprised of runtime tuning of the serverbased on real client search patterns, number of directory entries andthe average size of entry.

A further embodiment of the invention, described in detail below,provides a number of important features including auto tuning of LDAPserver cache, auto tuning of buffer pool (database cache), and runtimetuning of critical database parameters. The LDAP server cache is thefirst place which should be tuned properly by the administrators,because it is first place where the server looks for the entriesrequested by the client SEARCH requests. If entry is not found in theLDAP server cache, then database query is executed to search for theentry in the LDAP database. The LDAP database buffer pool is thedatabase cache, which is looked for if the entries are not found in theLDAP server cache. It is always recommended to have some optimum valuefor LDAP database buffer pools so that there is no overhead in searchingthe requested entry in the database tables. Every database that is usedwith the LDAP server comes with a set of tuning parameters that can betuned to avail optimal performance of the server.

Further benefits and advantages of this invention will become apparentfrom a consideration of the following detailed description, given withreference to the accompanying drawings, which specify and show preferredembodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary distributed data processing system in whichembodiments of the invention may be implemented.

FIG. 2 is an exemplary server-computing device that may be used as anLDAP server in FIG. 1.

FIG. 3 is an exemplary a client device that may be used with an LDAPdirectory server in FIG. 1.

FIG. 4 illustrates an exemplary embodiment of a high-level control flowto trigger performance of a tuning operation.

FIG. 5 illustrates an exemplary embodiment of the type of tuningperformed.

FIG. 6 illustrates an exemplary embodiment of an operation within aBasic Tuning Module.

FIG. 7 describes exemplary embodiments of several engines within anAdvanced Tuning Component.

FIG. 8 illustrates an exemplary embodiment of an operation of the FilterCollection and Parsing Engine of FIG. 7.

FIG. 9 describes an exemplary embodiment of the logic flow of operationperformed by the Advanced Tuning Module.

FIG. 10 illustrates an exemplary embodiment of a database health checkoperation that is performed in the Advanced Tuning Module.

FIG. 11 is an exemplary embodiment of a table that describes severalattributes that may be used.

DETAILED DESCRIPTION

Embodiments of the invention provide a system, an apparatus and a methodfor autonomous tuning of the LDAP servers and directory databases. Assuch, embodiments of the invention may be implemented in an LDAPdirectory server computing device which is part of a distributed dataprocessing system. Therefore, a brief explanation of a distributed dataprocessing environment will first be provided in order to give a contextto the description of the preferred embodiment of the present invention.

Reference is now made to FIG. 1, which depicts a pictorialrepresentation, by way of an exemplary embodiment, of a network of dataprocessing systems in which embodiments of the invention may beimplemented. Network data processing system 100 is a network ofcomputers in which embodiments of the invention may be implemented.Network data processing system 100 contains a network 102, which is themedium used to provide communications links between various devices andcomputers connected together within network data processing system 100.Network 102 may include connections, such as wire, wirelesscommunication links, or fiber optic cables.

In the example depicted, server 104 is connected to network 102 alongwith storage unit 106. In addition, clients 108, 110, and 112 areconnected to network 102. These clients 108, 110, and 112 may be, forexample, personal computers or network computers. In this example,server 104 provides data, such as boot files, operating system images,and applications to clients 108-112. Clients 108, 110, and 112 areclients to server 104. Network data processing system 100 may includeadditional servers, clients, and other devices not shown.

In the example illustrated, network data processing system 100 is theInternet with network 102 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, government,educational and other computer systems that route data and messages. Ofcourse, network data processing system 100 also may be implemented as anumber of different types of networks, such as for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIG. 1 isintended as an example, and not as an architectural limitation for theembodiments of this invention.

Reference is now made to FIG. 2, an exemplary embodiment of a blockdiagram of a data processing system that may be implemented as a server,such as server 104 in FIG. 1. Data processing system 200 may be asymmetric multiprocessor (SMP) system including a plurality ofprocessors 202 and 204 connected to system bus 206. Alternatively, asingle processor system may be employed. Also connected to system bus206 is memory controller/cache 208, which provides an interface to localmemory 209. I/O bus bridge 210 is connected to system bus 206 andprovides an interface to I/O bus 212. Memory controller/cache 208 andI/O bus bridge 210 may be integrated as depicted.

Peripheral component interconnect (PCI) bus bridge 214 connected to I/Obus 212 provides an interface to PCI local bus 216. A number of modemsmay be connected to PCI local bus 216. Typical PCI bus implementationswill support four PCI expansion slots or add-in connectors.Communications links to clients 108-112 in FIG. 1 may be providedthrough modem 218 and network adapter 220 connected to PCI local bus 216through add-in boards.

Additional PCI bus bridges 222 and 224 provide interfaces for additionalPCI local buses 226 and 228, from which additional modems or networkadapters may be supported. In this manner, data processing system 200allows connections to multiple network computers. A memory-mappedgraphics adapter 230 and hard disk 232 may also be connected to I/O bus212 as depicted, either directly or indirectly.

A person of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 2 may vary from the components that are shown. Forexample, other peripheral devices, such as optical disk drives and thelike, may also be used in addition to or in place of the hardwaredepicted. The depicted example is not meant to imply architecturallimitations with respect to any of the embodiments of the invention. Thedata processing system depicted in FIG. 2 may be, for example, ancomputer system or a portable electronic system, running an operatingsystem, for example the UNIX or the LINUX operating system.

With reference now to FIG. 3, an exemplary embodiment of a block diagramillustrating a data processing system is depicted in which embodimentsof the invention may be implemented. Data processing system 300 is anexample of a client computer. Data processing system 300 employs aperipheral component interconnect (PCI) local bus architecture. Althoughthe depicted example employs a PCI bus, other bus architectures such asAccelerated Graphics Port (AGP) and Industry Standard Architecture (ISA)may be used. Processor 302 and main memory 304 are connected to PCIlocal bus 306 through PCI bridge 308. PCI bridge 308 also may include anintegrated memory controller and cache memory for processor 302.Additional connections to PCI local bus 306 may be made through directcomponent interconnection or through add-in boards.

In the example given in FIG. 3, local area network (LAN) adapter 310,SCSI host bus adapter 312, and expansion bus interface 314 are connectedto PCI local bus 306 by direct component connection. In contrast, audioadapter 316, graphics adapter 318, and audio/video adapter 319 areconnected to PCI local bus 306 by add-in boards inserted into expansionslots. Expansion bus interface 314 provides a connection for a keyboardand mouse adapter 320, modem 322, and additional memory 324. Smallcomputer system interface (SCSI) host bus adapter 312 provides aconnection for hard disk drive 326, tape drive 328, and CD-ROM drive330. Typical PCI local bus implementations will support three or fourPCI expansion slots or add-in connectors.

An operating system runs on processor 302 and is used to coordinate andprovide control of various components within data processing system 300in FIG. 3. The operating system may be a commercially availableoperating system, such as Windows XP, which is available from MicrosoftCorporation. An object oriented programming system such as Java may runin conjunction with the operating system and provide calls to theoperating system from Java programs or applications executing on dataprocessing system 300. “Java” is a trademark of Sun Microsystems, Inc.Instructions for the operating system, the object-oriented operatingsystem, and applications or programs are located on storage devices,such as hard disk drive 326, and may be loaded into main memory 304 forexecution by processor 302.

A person of ordinary skill in the art will appreciate that the hardwarein FIG. 3 may vary depending on the implementation. Other internalhardware or peripheral devices, such as flash read-only memory (ROM),equivalent nonvolatile memory, or optical disk drives and the like, maybe used in addition to or in place of the hardware depicted in FIG. 3.Also, the processes of the embodiments of the invention may be appliedto a multiprocessor data processing system.

As a further example, data processing system 300 may be a stand-alonesystem configured to be bootable without relying on some type of networkcommunication interfaces. As a further example, data processing system300 may be a personal digital assistant (PDA) device, which isconfigured with ROM and/or flash ROM in order to provide non-volatilememory for storing operating system files and/or user-generated data.

The example in FIG. 3 and above-described examples are not meant toimply architectural limitations. For example, data processing system 300also may be a notebook computer or hand held computer in addition totaking the form of a PDA. Data processing system 300 also may be a kioskor a Web appliance.

As mentioned above, embodiments of the invention provides a method andsystem for autonomous tuning of LDAP servers and directory databases;and FIG. 4 describes an exemplary embodiment of the high-level controlflows, to trigger the performance tuning operation that is Basic Tuningor Advanced Tuning or both.

As indicated in FIG. 4, three conditions are taken into account beforethese tuning operations are triggered. A first of these conditions,represented at 402, is that the value of an attributePerf_tuning_enabled is set to true. A second condition, represented at404, is that the Tperftune thread is active because a specified time hasbeen reached; and the third condition, represented at 406, is thatTperftune thread is active because the LDAP cache hit ratio is below agiven threshold.

More specifically, the performance tuning operation is triggered in theserver by a server thread “Tperftune”. During server startup or inresponse to the extended operation, the tuning configuration entry inthe server configuration file is read i.e dn:cn=PERF,cn=configuration(See Table 1 of FIG. 11).

Syntax of LDAP ExOp to start Tperftune thread in server: ldapexop-D<binddn>-w<bind passoword>-op<TuningOp>

The details of the tuning entry are available in the Table 1 (FIG. 11).If the value of attribute Perf_tuning_enabled: is set to true, then theTperftune thread will be created and moved into inactive state. TheTperftune thread will become active for tuning operation based on eitherof the following the triggering conditions:

1. If the time specified in the attribute Perf_day, Perf_time in thetuning entry is reached; or

2. If the LDAP cache hit ratio falls below the configurable thresholdvalue. The threshold value is a configurable parameter defined as anattribute value pair in the tuning entry dn:cn=Perf, cn=configuration;or

3. If the administrator issues the extended operation.

As indicated in FIG. 4 and FIG. 5, the types of tuning can be performedin the implementation of an embodiment of the invention. These types oftuning are referred to as Basic Tuning, represented at 420 in FIGS. 4and 5, and Advanced Tuning, represented at 430 in FIGS. 4 and 5. BasicTuning consists of more of static tuning of the directory server basedon the total number of entries present in the database, the average sizeof entry present in the database, and a few configurable parameters thatcan be set by the administrator.

Based on these values, the directory server tunes all the performancetuning factors, which is basically comprised of LDAP Cache and directorydatabase cache. Basic tuning module can be triggered on server startupby reading server configuration file or using LDAP ExOp. The details ofthe configuration entry and its parameters are available in Table 1(FIG. 11). Basic tuning module analyzes and tunes LDAP server cache anddatabase buffer pools, which are considered to be the most criticaltuning factors to improve the performance of directory server.Administrator can opt for Basic Tuning operation during servermaintenance period or during deployment of the server by feeding in allthe inputs in the configuration entry for performance. This activityneeds to be repeated at regular interval to keep the LDAPserver/database tuning parameter acceptable condition.

FIG. 6 describes the operation, generally referenced at 600, that isperformed by Basic tuning module. In LDAP, the performance factor islargely dependent on the cache available to store the LDAP entries. Thepriority would be given to LDAP cache followed by database buffer pools.If the size of these caches is large, fewer expensive disk I/O's areneeded. The Entry Cache in the LDAP, where all entries are stored, isone of the most important caches that affects the performance of LDAPserver. The Basic Tuning module evaluates the size of system memory thatis allotted to LDAP sever and the Entry Cache size requirement is basedon the configuration parameters Perf_system_memory_alloted,Perf_total_entry, Perf_avg_entry_size. These parameters are described inmore detail in Table 1 (FIG. 11). If the amount of system memoryallotted to LDAP server (specified by administrator as a tuning entryconfiguration parameter) is large enough to handle the current entrycache size, then the LDAP Entry Cache is modified to new size that iscomputed by the following formulas:

(Perf_system_memory_alloted*getFreeSystemMemory( )/100>

(Perf_entry_cache_quota*Perf_total_entry)*Perf_avg_entry_size

LDAP entry cache=(Perf_entry_cache_quota*Perf_total_entry)

LDAP entry cache is total number of entry to be cached in the server.

Since database buffer pool is the next target area for performance, allthe LDAP System memory left over is preferably assigned to these bufferpools i.e.

(Perf_system_memory_alloted*getFreeSystemMemory()/100−(Perf_entry_cache_quota*Perf_total_entry)*Perf_avg_entry_size

Table 1 (FIG. 11) provides a more detailed description of all theattributes mentioned in the formulae given above.

Advanced tuning is comprised tuning of directory server based on thereal client search patterns, number of directory entries and the averagesize of the entry. Real customer search patterns are collected andstored in the flat files and are used at regular intervals, for example,based on the time interval specified in the configuration attribute(Ref: Table 1), by the advanced tuning engine to stress, analyze andtune directory server cache and RDBM buffer pools and several databaseparameters to gain optimal performance from server. This module thuscovers Basic Tuning operation along with other critical parametertuning. Like basic tuning, advanced tuning is also performed at runtimeif any one of the conditions as shown in FIG. 4 is met. This tuning isdone based on the configuration parameters present in the tuningconfiguration entry (See Table 1). Advanced tuning operation isinitiated by the “Tperftune” thread of the server, if either of thefollowing condition is satisfied:

1. If the time specified in the attribute Perf_day, Perf_time in thetuning entry dn:cn=Perf, cn=configuration is reached; or

2. If the LDAP cache hit ratio falls below a threshold value. Thethreshold value is a configurable parameter defined as an attributevalue pair in the tuning entry dn:cn=Perf, cn=configuration; or

3. If administrator issue extended operation.

FIG. 7 shows an exemplary embodiment of the Workload Engine 710 that isused in the Advanced Tuning, and several engines within that WorkloadEngine. The Workload Engine is responsible for stressing the serverbased on real customer search patterns, analyzing the results and fortuning of the directory server. The preferred embodiment of the WorkloadEngine includes a Filler Collection and Parsing Engine 720, a StressEngine 730, an Analyzer Engine 740, and a Tuning Engine 750.

The Filter Collection and Parsing Engine 720 is used to collect the realcustomer search patterns. The parser is used to parse the searchrequests and to store the search filter, scope of search and DN in aflat file. Each pattern stored will be unique in itself. The StressEngine 730 is used to stress the server. This basically comprisesreading the search patterns stored in the flat files and triggeringmultiple searches (i.e SearchA, SearchB, . . . SearchN) using multipleclients and multiple threads within the same client to stress thedirectory server. The search operation triggered is based on the realcustomer search patterns collected by the Filter collection and Parsingengine. It may be noted that administrators are suggested to performthis activity in the time period when the server toad is less. (i.e.,when the number of client operations is small, or during maintenanceperiod) as, when tuning operation is being performed by this engine, theperformance of the server might be impacted.

The Analyzer Engine 740 is used to analyze directory server and databaseparameters. Parameters analyzed by this engine include the LDAP cache,the Database buffer pools, and the database parameters. Once the StressEngine performs its task, the Analyzer engine starts its operationdescribed below.

First, the Analyzer Engine fetches the total number of entries and theaverage size of entries present in the database. This can be obtainedfrom the table where all the entries and the size of each entry arestored. Next, the Analyzer Engine evaluates the health of the databaseparameters. Every database vendor provides set of database configurationparameters and methods of tuning these parameters so as to achieveoptimal performance out of the database management system. This can betaken as a reference in this design.

The next step is to evaluate the LDAP cache hit ratio. If the ratio isbelow the threshold value as defined under the tuning entry “cn=Perf,cn=configuration”, then the “TuningRequired” flag is set to true. Thisis an indication that the entire tuning cycle needs to be repeated aftertuning the value of LDAP cache, RDBM buffer pools and RDBM parameters byinvoking Tuning Engine. The tuning cycle should be executed again tocheck if new value set aside for the tuning parameters is optimal.

If this is the first iteration, then the next step is to analyze thethroughput of server for LDAP search operation and store it in memory,else analyze the throughput of server for LDAP search operation andcompare the throughput with the value stored in previous pass. If thedifference in the value is within the tolerable limit, then the“TuningRequired” flag is set to false. This is an indication that theLDAP server and database tuning parameters are tuned to their optimalvalue. If the difference in the value is not within the tolerable limit,then the “TunningRequired” flag is set to true. This cycle is repeateduntil an optimal performance of LDAP server and values for the tuningparameters are obtained.

The Tuning Engine 750 is used to tune the directory server and databaseparameter. Parameters tuned by this engine include the LDAP cache, theRDBM buffer pools, and the RDBM configuration parameters. Once Analyzerengine performs its task, the Tuning Engine start its operation asfollows. First, the LDAP cache is tuned based on the figures collectedby analyzer engine (more details are given in FIG. 9). Then, thedatabase buffer pool is tuned (for more detail, see FIGS. 9 and 10).Next, the database configuration parameters are tuned based on thehealth of these parameters computed by Analyzer Engine. If the values ofthe database parameters are above or below the expected values, thenthey are tuned.

FIG. 9 describes an exemplary embodiment of the logic flow for tuningRDBM performance tuning parameter. The flowchart of FIG. 9 describes thelogic flow of operations performed by the Advanced Tuning module. Inthis procedure, a client search pattern is read at step 902, and then,at step 904, the stress engine is used to stress the server. At step906, the Analyzer Engine is used to analyze the results of the stresstest; and at step 910, it is determined whether tuning is required. Iftuning is not required, the procedure of FIG. 9 ends. However, if tuningis required, then, at step 912, the Tuning Engine is invoked to performthat tuning; and after the tuning is completed, the procedure returns tostep 902 and continues on from there.

FIG. 10 shows am exemplary embodiment of a database health checkoperation that is performed in the Advanced Tuning module. As will beunderstood a person of ordinary skill in the art, all databasesgenerally come with a set of configurable parameters, and theseparameters are used as a basis for the database health check module.

In the health check procedure illustrated in FIG. 10, at step 1002, adatabase connection is established, and at step 1004, a snapshot of thedatabase is obtained. A suitable health check operation is performed onseveral database parameters at step 1006; and at step 1008, the healthof the database parameters is analyzed based on the performed healthcheck operation. Then, at step 1010, it is determined whether eachdatabase parameter needs to be increased or decreased. If a databaseparameter needs to be increased, then its value is increased at step1012; and analogously, if a database parameter needs to be decreased,then, at step 1014, the value of that parameter is decreased.

As will be readily apparent to a person skilled in the art, embodimentsof the invention can be realized in hardware, software, or a combinationof hardware and software. Any kind of computer/server system(s)—or otherapparatus adapted for carrying out the methods described herein—issuited. A typical combination of hardware and software could be ageneral-purpose computer system with a computer program that, whenloaded and executed, carries out the respective methods describedherein. Alternatively, a specific use computer, containing specializedhardware for carrying out one or more of the functional tasks of theinvention, could be utilized.

Aspects of the invention, can also be embodied in a computer programproduct, which comprises all the respective features enabling theimplementation of the methods described herein, and which—when loaded ina computer system—is able to carry out these methods. Computer program,software program, program, or software, in the present context mean anyexpression, in any language, code or notation, of a set of instructionsintended to cause a system having an information processing capabilityto perform a particular function either directly or after either or bothof the following: (a) conversion to another language, code or notation;and/or (b) reproduction in a different material form.

While it is apparent that the invention herein disclosed is wellcalculated to fulfill the objects stated above, it will be appreciatedthat numerous modifications and embodiments may be devised by thoseskilled n the art, and it is intended that the appended claims cover allsuch modifications and embodiments as fall within the true spirit andscope of the present invention.

1. A method of autonomously tuning a Lightweight Directory AccessProtocol (LDAP) server, wherein the server includes a server cache andbeing configured to access an LDAP database, the method comprising:activating a tuning thread when defined conditions are met; and usingthe tuning thread to initiate automatically a tuning procedure to tunethe LDAP server cache, to tune a database buffer pool for the server,and to perform runtime tuning of given parameters of the LDAP database.2. The method as claimed in claim 1, wherein the defined conditionsinclude at least one of reaching a specified time or is a cache hitratio of the server falling below a given threshold value or includes anexecution to start a tuning operation.
 3. The method as claimed in claim1, wherein the tuning procedure includes static tuning of the serverbased on the total number of entries in the database and the averagesize of said entries.
 4. The method as claimed in claim 1, wherein theusing said tuning thread for a specified amount of a defined memoryspace includes: checking a defined set of parameters; and based onresults of the checking the defined set of parameters, increasing theamount of the defined memory space allocated to the server cache, andallocating all of the remaining of the defined memory space to thebuffer pool.
 5. The method as claimed in claim 1, wherein the tuningprocedure includes runtime tuning of the server based on real clientsearch patterns and the type of data uploaded on the server.
 6. Themethod as claimed in claim 5, wherein the using said tuning threadsincludes: collecting and storing real customer search patterns; andusing the customer search patterns to stress, analyze and tune theserver cache, the database buffer pool, and the given parameters whenone of the defined conditions is met.
 7. The method as claimed in claim6, wherein the using the Customer search patterns includes reading thestored search patterns, and triggering multiple searches using multipleclient and multiple threads within the same client to stress the server.8. The method as claimed in claim 7, wherein the analyzing results ofstressing the server includes: fetching the total number of entries andthe average size of entries present in the database; and evaluating thehealth of a defined set of database parameters according to definedcriteria.
 9. A method for tuning an LDAP server, the method comprising:monitoring performance of an LDAP server; identifying instructions to beexecuted based on a pre-defined condition; executing the identifiedinstructions to adjust parameters of the LDAP server, whereby theperformance of the LDAP server is enhanced.
 10. The method as claimed inclaim 9, wherein the predefined condition comprises at least one of (i)a time-related attribute reaching predetermined levels; (ii) a cache-hitratio being less than a predetermined threshold; and (iii) detecting anextended operation condition, the extended operation being used todefine operations performed by the LDAP server.
 11. The method asclaimed in claim 10, wherein identifying instructions comprises:identifying a first set of instructions to be executed when at least oneof (i) the time-related attribute reaches a predetermined level; (ii)the cache-hit ratio is less than a predetermined threshold; andidentifying a second set of instructions to be executed upon detectingthe extended operation condition.
 12. The method as claimed in claim 11,wherein the first set of instructions comprises: collecting real-timecustomer search patterns; preparing a workload based on the collectedsearch patterns; testing stability of the LDAP server based on theprepared workload; during testing, preparing an analysis on thestability of the LDAP server; and adjusting the parameters of the LDAPserver based on the analysis.
 13. The method as claimed in claim 11,wherein the second set of instructions comprises: computing amount ofmemory allocated to the LDAP server; identifying amount of memoryrequired to store data in the LDAP server; on determining the amount ofmemory allocated to the LDAP server being less than the amount of memoryrequired to store the data, adjusting the parameters of the LDAP serverto result in an amount of memory sufficient to store the data in theLDAP server.
 14. A system of autonomously tuning a Lightweight DirectoryAccess Protocol (LDAP) server, wherein the server includes a servercache and being configured to access an LDAP database, the systemcomprising at least one processor configured for: activating a tuningthread when defined conditions are met; and using the tuning thread toinitiate automatically a tuning procedure to tune the LDAP server cache,to tune a database buffer pool for the server, and to perform runtimetuning of given parameters of the LDAP database.
 15. The system asclaimed in claim 14, wherein the defined conditions include at least oneof reaching a specified time or is a cache hit ratio of the serverfalling below a given threshold value or includes an execution to starta tuning operation.
 16. The system as claimed in claim 14, wherein thetuning procedure includes static tuning of the server based on the totalnumber of entries in the database and the average size of said entries.17. The system as claimed in claim 14, wherein the using said tuningthread for a specified amount of a defined memory space configured for:checking a defined set of parameters; and based on results of thechecking the defined set of parameters, increasing the amount of thedefined memory space allocated to the server cache, and allocating allof the remaining of the defined memory space to the buffer pool.
 18. Thesystem as claimed in claim 14, wherein the tuning procedure includesruntime tuning of the server based on real client search patterns andthe type of data uploaded on the server.
 19. The system as claimed inclaim 18, wherein the using said tuning threads is configured for:collecting and storing real customer search patterns; and using thecustomer search patterns to stress, analyze and tune the server cache,the database buffer pool, and the given parameters when one of thedefined conditions is met.
 20. The system as claimed in claim 19,wherein the using the customer search patterns includes reading thestored search patterns, and triggering multiple searches using multipleclient and multiple threads within the same client to stress the server.21. The system as claimed in claim 20, wherein the analyzing results ofstressing the server includes: fetching the total number of entries andthe average size of entries present in the database; and evaluating thehealth of a defined set of database parameters according to definedcriteria.
 22. A system for tuning an LDAP server, the system comprisingat least a processor and a memory being configured for: monitoringperformance of an LDAP server; identifying instructions to be executedbased on a pre-defined condition; executing the identified instructionsto adjust parameters of the LDAP server, whereby the performance of theLDAP server is enhanced.
 23. The system as claimed in claim 22, whereinthe predefined condition comprises at least one of (iv) a time-relatedattribute reaching predetermined levels; (v) a cache-hit ratio beingless than a predetermined threshold; and (vi) detecting an extendedoperation condition, the extended operation being used to defineoperations performed by the LDAP server.
 24. The system as claimed inclaim 23, wherein identifying instructions comprises: identifying afirst set of instructions to be executed when at least one of (iii) thetime-related attribute reaches a predetermined level; (iv) the cache-hitratio is less than a predetermined threshold; and identifying a secondset of instructions to be executed upon detecting the extended operationcondition.
 25. The system as claimed in claim 24, wherein the first setof instructions comprises: collecting real-time customer searchpatterns; preparing a workload based on the collected search patterns;testing stability of the LDAP server based on the prepared workload;during testing, preparing an analysis on the stability of the LDAPserver; and adjusting the parameters of the LDAP server based on theanalysis.
 26. The system as claimed in claim 24, wherein the second setof instructions comprises: computing amount of memory allocated to theLDAP server; identifying amount of memory required to store data in theLDAP server; on determining the amount of memory allocated to the LDAPserver being less than the amount of memory required to store the data,adjusting the parameters of the LDAP server to result in an amount ofmemory sufficient to store the data in the LDAP server.
 27. A computerprogram product comprising a computer readable medium having a computerusable program embodied therewith, the computer usable code configuredto perform the method as claimed in claim
 1. 28. A computer programproduct comprising a computer readable medium having a computer usableprogram embodied therewith, the computer usable code configured toperform the method as claimed in claim 9.